The OpenAPI Normalizer wraps $ref with sibling properties (title, description) inside allOf constructs. The Protobuf generator wasn't properly unwrapping these single-item allOf containers, causing issues when handling complex types within oneOf.
expected:

Pet:
  oneOf:
    - allOf:  
        - $ref: '#/components/schemas/Dog'
      title: dog
      description: "A dog pet"
    - allOf:  
        - $ref: '#/components/schemas/Cat'
      title: cat
      description: "A cat pet"
    - allOf:  
        - $ref: '#/components/schemas/Bird'
      title: bird
      description: "A bird pet"

solution:
Unwrap single-item allOf: If the resolved schema is allOf with exactly one item, unwrap it.

Pet:
  oneOf:
    - title: dog  
      description: "A dog pet"
      $ref: '#/components/schemas/Dog'
    - title: cat  
      description: "A cat pet"
      $ref: '#/components/schemas/Cat'
    - title: bird  
      description: "A bird pet"
      $ref: '#/components/schemas/Bird'

PR checklist

• Read the contribution guidelines.
• Pull Request title clearly describes the work in the pull request and Pull Request description provides details about how to validate the work. Missing information here may result in delayed response from the community.
• Run the following to build the project and update samples:

  ./mvnw clean package || exit
  ./bin/generate-samples.sh ./bin/configs/*.yaml || exit
  ./bin/utils/export_docs_generators.sh || exit
  

  (For Windows users, please run the script in WSL)
  Commit all changed files.
  This is important, as CI jobs will verify all generator outputs of your HEAD commit as it would merge with master.
  These must match the expectations made by your contribution.
  You may regenerate an individual generator by passing the relevant config(s) as an argument to the script, for example ./bin/generate-samples.sh bin/configs/java*.
  IMPORTANT: Do NOT purge/delete any folders/files (e.g. tests) when regenerating the samples as manually written tests may be removed.
• File the PR against the correct branch: master (upcoming 7.x.0 minor release - breaking changes with fallbacks), 8.0.x (breaking changes without fallbacks)
• If your PR solves a reported issue, reference it using GitHub's linking syntax (e.g., having "fixes #123" present in the PR description)
• If your PR is targeting a particular programming language, @mention the technical committee members, so they are more likely to review the pull request.